Information archival and retrieval system for internetworked computers

ABSTRACT

A computing system can archive information from internetworked computers, such as Internet content, for later retrieval. A server system processes content providers, such as DNS registries and web sites, to extract and store content, including text, image, audio, and video content. For web sites, HTML source code is stored along with a browser-rendered display file. The content is perpetually archived to create a historical record of information for each content provider. An interface is used to retrieve the archived content in response to queries.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.12/873,289, filed on Aug. 31, 2010, which is a continuation of U.S.application Ser. No. 09/909,502, filed Jul. 19, 2001 (now U.S. Pat. No.7,792,682), which claims the benefit of U.S. Provisional Application No.60/219,515, filed Jul. 20, 2000. The entire teachings of the aboveapplications are incorporated herein by reference.

BACKGROUND

The Internet is a vast internetwork of individual computers and computernetworks used to share information. Every computer connected to theInternet has a unique Internet Protocol (IP) address. The IP addressesare used to route messages between computers across the Internet andthrough user networks. Using the IP addresses, any two computers cancommunicate with one another. In its most basic form, the Internet canbe used as a peer-to-peer network. Such a paradigm can be exploited toexchange files between computers, such as File Transport Protocol (FTP)applications. A more common model is the client-server model where webservers store and transmit information, in the form of web pages, toclients upon request. Another application of client-server applicationsis a newsgroup, where clients can exchange information through a newsserver.

The Internet, in whatever form, is largely open and unmanaged. Anyonewith a computer can connect to the Internet to gather or shareinformation. In addition, any computer can be added to or removed fromthe Internet at will. Moreover, the information on any given computercan be changed at will. Consequently, the information available on theInternet is extremely fluid.

Because of the Internet's rapidly changing nature, searching forinformation is limited to viewing snapshots of the Internet. Althoughmany search engines are available to search the Internet, they allsuffer from a similar problem. Namely, information found and indexed bya search engine at a particular time may not exist at a later time—whenit is needed. Thus, a search engine may report relevant search resultsbut the underlying information may have since been removed from theInternet. A researcher using the search engine can be stymied by stalelinks to the now nonexistent information.

Eventually, the search engine may purge its database of the old and nownonexistent information. In other words, the search engine may no longerreport that the information ever existed. Unless the informationreappears, it can be lost forever.

SUMMARY

There are times when a researcher seeks historical records ofinformation. Although news reporting services typically archive newsarticles, they only archive their own content and may restrict access tothe archived data. Unlike professional news services, individual andcorporate web sites and other Internet nodes do not publicly archivetheir content at all. Although a user may backup versions of its website, the backup copies are controlled by the user and may not beavailable to others. Those content providers may account for the bulk ofthe information on the Internet.

The information sought by a searcher can depend on various factors.Typical information includes web site content. The information may alsoinclude metatags or internal source coding. The searcher may be anindividual researcher looking for specific publications or aprofessional researcher looking for specific acts on the Internet.

Of particular interest are legal researchers defending intellectualproperty rights. For example, a trademark searcher might be interestedin all uses of a particular mark, from its use on a web page or itsexistence in a web page's metatags. A copyright searcher might beinterested in the existence of works on web pages. Similarly, a patentsearcher might be interested in offers to sell products on web sites. Aresearcher may also want to trace the evolution of a known web site overtime to, for example, measure damages caused by the site. The technologyto do these searches, alone or in combination, is not currentlyavailable.

A suitable solution has not existed because, in part, of the quantity ofdata that must be stored. The storage requirements become unmanageablefor real-time systems. As long as results do not need to be provided toa user in real time, most of the information can be stored offline.

In accordance with an aspect of the invention, a system for storinginformation for later retrieval can include a plurality of archived datafiles in storage, including a plurality of archived media files copiedfrom a specific electronic address over time, where each archived mediafile having a version of authored content stored therein as collectedfrom the specific electronic address at a specific time. The system canalso include a searchable electronic index of the authored contentstored within the archived media files, with the electronic indexincluding references to the archived media files. A query engine can bein communication with the electronic index for retrieving an archivedmedia file based on a query parameter and the electronic index.

Another embodiment of a system for storing information for laterretrieval can include a plurality of archived data files in storage,including a plurality of archived rendered files associated with aspecific electronic address over time, where each archived rendered filehaving a version of rendered content stored therein. Furthermore, therendered content can include an image of a browser display responsive tooperation of a respective source file as accessed from the specificelectronic address at a specific time. The system can also include asearchable electronic index of the rendered content stored within thearchived rendered files. A query engine can be in communication with theelectronic index for retrieving an archived rendered files based on aquery parameter and the electronic index.

Yet another embodiment of a system for storing information for laterretrieval can include a plurality of archived data files in storage,including a plurality of archived original source files associated witha specific electronic address over time and a plurality of archivedrendered files. Each archived original source file can have a version ofauthored content stored therein as collected from the specificelectronic address at a specific time and each archived rendered filecan have a version of rendered content stored therein, where therendered content including an image of a browser display responsive tooperation of a respective archived original source file. A database canassociate the archived source files with the archived rendered files.The system can also include a searchable electronic index of theauthored content stored within the archived original source files andthe rendered content stored within the archived rendered files, wherethe electronic index including references to the archived originalsource files and the archived rendered files. A query engine can be incommunication with the electronic index for retrieving the archived datafiles based on a query parameter and the electronic index.

In accordance with still another aspect of the invention, a systemstoring information for retrieval can include a database, processingmodules, and a query engine.

The database stores data in an organized structure. The data can beassociated with stored content from internetworked content providers. Inparticular, an archive can store the stored content in perpetuity. Thedatabase can include references to the stored content for retrieval fromthe archive.

The modules can be used to populate the database with data. The modulescan, in turn, be in communication with the content providers, such asover a public access computer network like the Internet. The contentproviders can include content providers selected from domain nameservice registries and web servers.

The query engine can be responsible for retrieving the stored contentbased on a query parameter. The system can further include an indexer,the indexer creating a searchable index of the stored content. Inparticular, the index is a multimedia indexer. Using these tools, thestored content can be searched based on text, audio, video, or imagecontent.

In accordance with another aspect, the invention can be embodied in acomputerized system for the storage and retrieval of content fromInternet content providers. The content can include registration contentand page content.

The system can include a data warehouse structured to store content forlater retrieval. The data warehouse can include a database structure formanaging the stored content.

The system can also include a registration retrieval mechanism incommunication with Internet registries for retrieving registrationcontent for content providers. The retrieved content can then be storedin the data warehouse.

The system can include a page retrieval mechanism in communication witha content provider for retrieving page content from the contentproviders. The retrieved page content can then be stored in the datawarehouse.

The system can include an indexer for indexing the stored content. Aquery engine can be coupled to the indexer for retrieving storedcontent. In particular, the indexer is a multimedia indexer. A user canthus find stored content based on text, audio, video, or image content.Furthermore, the query engine includes a program interface operable by aremote computer.

In accordance with another aspect, the invention can be embodied in acomputerized system for archiving information from internetworked webcontent providers.

In this system, an identifier of a web content provider can be stored ina data warehouse. The identifier can be a unique address of the webcontent provider, such as a domain name or IP address. The domain namecan be derived from a domain name registry. The data warehouse caninclude an offline storage medium.

For the web content provider, other information stored in the datawarehouse can include a copy of registration data, a copy of source codefor operating a web browser, and a copy of a browser-rendered displaygenerated by the source code files. The stored information can include acopy of a multimedia file. To save storage space, the stored informationcan be compressed by a compression algorithm.

A database can then associate the web content provider with the storedinformation. An indexer can also be provided to operate on the storedinformation. In particular, the indexer can include a digital signatureengine operating on multimedia files.

The system can also include a user interface for querying the datawarehouse. The user interface can be operable by a remote computer, suchas through includes a third-party search engine interface.

In particular, the system can include web robots to retrieve informationfrom a remote content provider. The remote content provider can be aregistry storing the registration data or the web content providerstoring the source code. The web content provider and the registry cansupport a protocol to facilitate the archival of information.

The system can further include a processing module to monitor changes tosource code at the web content provider, based on the stored sourcecode. In particular, the data warehouse stores a prior version and acurrent version of a changed source code file.

The system can further include a processing module to monitor changes toregistration data at a registration content provider based on the storedregistration data. In particular, the data warehouse stores a priorversion and a current version of changed registration data.

In accordance with yet another aspect, the invention can be embodied ina computerized system for archiving data from distinct contentproviders, each associated with at least one publicly accessible filerepresenting content. The system can include an identification for eachcontent provider of multiple content providers and a mechanism thatstores, for each identified content provider, the content of at leastone publicly accessible file in a data archive for later retrieval. Thestored content can be maintained in perpetuity.

In particular, the content providers are registered in a shared registrysystem. In addition, the at least one publicly accessible file includesregistration data associated with the registry. The content provider canbe identified by a unique address, such as a domain name or IP address.

The mechanism can include a data compression algorithm to reduce thesize of the at least one file before storing the content in the dataarchive.

A database structure can be employed to associate each content providerwith its stored content. The database structure can, in particular,track changes to the stored content over time.

The system can further include an indexer for maintaining a searchableindex of the stored content. In particular, the indexer supportsmultimedia content. A query engine can be coupled to the indexer forprocessing queries against the stored content. The query engine caninclude a program interface operable by a remote computer.

In accordance with another aspect, the invention can be embodied in acomputerized system for retrieving information from internetworkedcontent providers. The system can include a user interface and a queryresult.

The user interface can be in communication with a data warehouse havingstored information. The data warehouse can be located remote from theuser interface. The user interface can be used to solicit a query from auser. The query can solicit at least one of an Internet domain name, aUniversal Resource Locator, a text string, or a multimedia target. Theuser interface can, in particular, be a third-party search engine resultidentifying a Universal Resource Locator, which is responsive to thesolicitation for a query.

A query result can then be presented to the user in response to thequery. The query result can include obsolete information associated witha content provider. The query result can include a history of theinformation. The history can include changes to the information overtime. The changes can include changes to an Internet domain nameregistration or changes to information stored at a specified address.The query result need not be presented in real time, instead requiringdelayed access to offline storage.

The system can be particular useful for identifying users ofintellectual property. In this regard, the query results are responsiveto a query specifying a trademark (or service mark) or to a queryspecifying a work of authorship.

A more particular aspect of the invention can be embodied in a userinterface for monitoring intellectual property rights acrossinternetworked content providers. The user interface can include a queryinterface to solicit information related to an intellectual propertyright and a report responsive to the query information, the reportincluding archived information associated at least one content provider.

The solicited information can be at least one of a trademark (or servicemark), a work of authorship, or an invention. The solicited informationcan be entered as a file location. The file can be at least one of atext file, an audio file, an image file, or a video file.

The report can include archived information associated with multiplenetwork registrars. Likewise, the report can include archivedinformation from multiple web content providers. The archivedinformation can, in particular, include obsolete information.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other objects, features and advantages of theinvention will be apparent from the following more particulardescription of particular embodiments of the invention, as illustratedin the accompanying drawings in which like reference characters refer tothe same parts throughout the different views. The drawings are notnecessarily to scale, emphasis instead being placed upon illustratingthe principles of the invention.

FIG. 1 is a schematic block diagram of a data archival and retrievalsystem for internetworked computers.

FIG. 2 is a detailed block diagram of portions of the server system ofFIG. 1.

FIG. 3 illustrates an exemplary Whois file of FIG. 2.

FIG. 4 illustrates an exemplary source code file of FIG. 2.

FIG. 5 illustrates an exemplary browser-rendered file of FIG. 2.

FIG. 6 is a flowchart of the method employed by the domain informationrobot 22 of FIG. 2.

FIG. 7 is a flowchart of the method employed by the registry retrievalrobot 32 of FIG. 2.

FIGS. 8A-8C are flowcharts of the method of the page retrieval robot 42of FIG. 2.

FIG. 9 is a flowchart of the method of the user interface module 50 ofFIG. 2.

FIG. 10 illustrates an exemplary user interface for the query selectionmethod of FIG. 9.

FIG. 11 illustrates an exemplary user interface for the domain querymethod of FIG. 9.

FIG. 12 illustrates an exemplary user interface for the page querymethod of FIG. 9.

FIG. 13 illustrates an exemplary user interface for the search enginepage query method of FIG. 9.

FIG. 14 illustrates an exemplary user interface for the text querymethod of FIG. 9.

FIG. 15 illustrates an exemplary user interface for the multimedia querymethod of FIG. 9.

FIG. 16 illustrates an exemplary user interface for the ad hoc querymethod of FIG. 9.

DETAILED DESCRIPTION

FIG. 1 is a schematic block diagram of a data archival and retrievalsystem for internetworked computers. The archival and retrieval system 1includes a server system 10 in communication with a publicly accessiblecommunication system, such as the Internet 2. The Internet interconnectsa plurality of computers and computer networks. Those computers include,but are not limited to, Domain Name Service (DNS) Registries 3, Internet(third-party) search engines 5, and World Wide Web (WWW) servers 7. Alsoshown is a subscriber 18, who is authorized to use the services of theserver system 10.

The server system 10 can be a clustered network of computers. The serversystem 10 stores information content from the Internet, such as web sitedata, for later retrieval. The data is stored in control database tables12 a and in files 12 b of a data warehouse 12 accessible by a pluralityof storage and retrieval modules. The data warehouse can be particularlysuited to store multimedia data, such as Oracle interMedia for Oracle8i, commercially available from Oracle Corporation of Redwood Shores,Calif. In a particular embodiment of the warehouse 12, the tables 12 aare stored in a medium directly coupled to the server 10, such as a diskdrive. In another embodiment, the files 12 b are not directly coupled tothe server 10, relying on delayed retrieval and access, such as througha manual or automated mechanical system. The length of time needed toretrieve information, however, does not limit the usefulness of thesystem.

A domain information module 20 is responsible for identifying web sitesfor archiving. A registry retrieval module 30 is responsible forobtaining domain name registry WHOIS information on domain names. Theresulting content from various DNS registries is stored in the warehouse12

A page retrieval module 40 is responsible for accessing individual website pages and archiving the available information content in thewarehouse 12. In general, the page retrieval module 40 is driven bydomain name information provided by the domain information module 20.The page retrieval module 40 can also include a spider or an autonomouscrawler robot 45 for independently identifying Internet resources, suchas web pages, to archive. Because there are currently many Internetsearch engines in use that also identify web pages, the search enginescan feed that data to the system. An indexer 15 creates and maintains afull-text, searchable index of the archived information.

User access to the archived information in the warehouse 12 (tables 12 aand files 12 b) is managed by a user interface module 50. User accesscan be provided online to the subscriber 18 or offline via a system user18′ to produce query reports. Both the subscriber 18 and system user 18′can perform queries of the data warehouse 12.

A program interface sub-module 55 of the user interface module 50provides access to archived information associated with a givenUniversal Resource Locator (URL) page. The program interface sub-module55 can also be accessed by the subscriber 18 and the system user 18′. Inaddition, Internet search engines 5 can subscribe to provide access tothe URL-based program interface sub-module 55 to provide their userswith the benefits of the archived information.

FIG. 2 is a detailed block diagram of the server system of FIG. 1. Asshown, the server system automatically archives web pages and otherInternet resources using software robots. In a basic embodiment, thearchive is driven by DNS registry data.

The domain information module 20 includes a domain information robot 22,a Registry Table 24, and a Domain Table 26. The registry retrievalmodule 30 includes a registry retrieval robot 32, a Whois Table 34, anda plurality of Whois files 39. The page retrieval module 40 includes apage retrieval robot 42, an optional autonomous page retrieval robot 43,a Page Table 44, a Source Table 46, a plurality of source files 47, aRender Table 48, and a plurality of rendered files 49.

The domain information robot 22 is responsible for querying the DNSregistries for domain names. The Registry Table 24 maintains query datafor each known domain name registry. Each record in the Registry Table24 includes a RegistryName text field, a LastQueryTime date field, and aQueryTime date field. As illustrated, the domain information robot 22queries the Registry Table 24, accesses data from the table, and updatesthe table data. Based on the Registry Table fields, the domaininformation robot 22 queries the appropriate domain registry. The tabledata can also be populated from other sources, including bulk data andautonomous spiders or crawlers.

The domain information robot 22 stores data received from the registriesin the Domain Table 26. Each record in the Domain Table 26 includes aRegistryPtr pointer field, a DomainName text field, a WhoisPtr pointerfield, and a TimeStamp date field. The Domain Table 26 stores the datathat drives much of the archival process.

For each record in the Domain Table 26, the registry retrieval robot 32reads data from the DomainName and RegistryPtr fields and performs aWHOIS query on that domain name in the appropriate registry. The datacan also be extracted from a bulk data file. The resulting Whoisinformation is stored in a simple text format as a Whois file 39, whichcan be compressed to save storage space. Information about the Whoisfile 39 is maintained in the Whois Table 34.

FIG. 3 illustrates an exemplary Whois file 39 of FIG. 2. As shown,various data fields stored by the registrar are provided in response tothe query, including the identity of the named registrant. As furthershown, the Whois query includes extraneous text supplied by theregistrar. The extraneous text can be stored but may be filtered fromthe file before storing, especially if the registrar may frequentlychange the text.

Each Whois file 39 has a respective record in the Whois Table 34. Eachrecord in the Whois Table 34 includes a Checksum integer field, aFilePtr pointer field, a PrevPtr pointer field, a NextPtr pointer field,and a TimeStamp date field. For each Whois file, a checksum is computedand stored in the Checksum field to authenticate the stored Whois file39. The PrevPtr and NextPtr fields are used to create a chain of Whoisrecords for a particular domain name. That is, a history report of Whoisdata can be requested and generated from the Whois Table 34 data, evenif the domain name registrant transfers from registrar to registrar.

The DomainName field of the Domain Table 26 also seeds the pageretrieval robot 42. Using the domain name, the page retrieval robot 42accesses the domain and retrieves all pages in that domain. Ofparticular interest is the WWW third level domain, but other third leveldomains can be processed using a similar method. The page retrievalrobot 42 downloads the page source files (e.g. HTML, JPEG, WAV, MPEG,MP3 files) and also the browser-displayed rendition of the pages (whenapplicable) and stores them as source files 47 and rendered files 49,respectively.

FIG. 4 illustrates an exemplary source code file 47 of FIG. 2. As shown,the file 47 is an HTML file. In addition to source for the displayedtext, metatags are also in the file and indexable. Other file formatsare also supported.

FIG. 5 illustrates an exemplary browser-rendered file 49 for the sourcecode file of FIG. 4. The rendition is generated from the source code bythe browser code.

Each page is identified by its URL. Each URL has an individual record inthe Page Table 44. The fields in the Page Table 44 include a URL textfield, a DomainPtr pointer field, and a CurrentSourcePtr pointer field.The DomainPtr points to the appropriate Domain Table 26 record for theURL. The CurrentSourcePtr points to an appropriate record in the SourceTable 46.

The Source Table 46 associates a database record with a stored sourcefile 47 and is populated by the page retrieval robot 42. The SourceTable 46 includes a UrlPtr pointer field, a Checksum integer field, aPageRenderPtr pointer field, a PrevSourcePtr pointer field, aNextSourcePtr pointer field, a FilePtr pointer field, and a TimeStampdate field. The UrlPtr points to the associated record in the Page Table44. The Checksum field stores the computed checksum of the source file47, which is pointed to by the FilePtr field. The PrevSourcePtr andNextSourcePtr fields point to previous and next records in the historychain of the URL. The PageRenderPtr points to an associated record inthe Render Table 48.

The Render Table 48 associates a database record with the storedrendered file 49. The Render Table 48 includes a Checksum integer field,a FilePtr pointer field, and a TimeStamp date field. As above, theChecksum field stores a computed checksum of the associated renderedfile 49, which is pointed to by the FilePtr field.

The autonomous page retrieval robot 43 can be useful in identifyingpages stored under other than WWW third-level domains, such as “ftp”,“people”, “sales”, etc. In this regard, the autonomous page retrievalrobot 43 can operate as a standard spider—following links from URL toURL—populating the Page Table 44 as it proceeds. This technique can beparticularly useful when the third-level domain is unusual. The systemcan also make use of web site registration as is commonly used by priorart Internet search engines.

The Indexer 15 maintains a searchable full-content index of the Whoisfiles 39, the source files 47, and the rendered files 49. The Indexer 15can be any suitable commercially-available indexer that can index thestored files. Those files can then be compressed for archival storage.In a particular embodiment, the rendered files 49 are stored in AdobePublic Display Format (PDF) for portability. The conversion from thenative format to the compressed format is accomplished by the registryretrieval and the page retrieval robots during the download process. Thechecksums are computed from the native Whois files, source files, andgenerated renditions before being compressed into the archived files 39,47, 49.

The user interface module 50 receives user requests and responds withreports 59. The user interface module 50 is generally used for broadqueries of the stored files 39, 47, 49. For example, a user may beinterested in all files that contain the trademark TRIEVE. The full-textindex would be used to identify all such files and the user interfacemodule would prepare a report of those files. This solution would reportall web sites and domain names, for example, that use the trademark indisplayed text as well as undisplayed text, such as metatags.

Using a suitable image signature engine, the indexer 15 can index andsearch both image source files and rendered pages to identify trademark(including service mark) use in images to combat cyberstuffing and toidentify digital signatures and watermarks from works if authorship tocombat copyright infringement. A particular image signature enginesuitable for computing digital signatures of and indexing image files isVisual Image Retrieval from Virage, Inc of San Mateo, Calif. Aparticular embodiment of the Virage technology is embodied in Oracle 8iVisual Image Retrieval, commercially available from Oracle Corporation.Similarly, signatures can be generated for other multimedia content,such as audio and video data. For example, the VideoLogger programcommercially available from Virage, Inc. can be integrated with theOracle database to facilitate indexing of video content. A suitableaudio recognition and signature engine is TRM, commercially availablefrom Relatable, LLC of Alexandria, Va.

The program interface module 55 provides narrow reports about aparticular URL, or second-level domain name. For example, a user may beinterested in a detailed history of a specific URL for a web page on itsweb server. The resulting report 59 can provide step-by-step details ofthe page's evolution over time, including ownership information andsource HTML.

It is recognized that information may exist on some web sites longerthan others. For example, news sites can be continuously updatedthroughout a day, while personal web sites may go months without anupdate. The page retrieval module 40 can be triggered to access certainidentified sites on an accelerated schedule. For most sites, an accessinterval of a few days should be sufficient. Alternatively, the server10 and the page can support a common protocol, where changes to a pagetrigger the page retrieval module 40.

In a particular embodiment of the system, the server modules share acommon protocol with the content providers 3, 7 so that information canbe retrieved easily. It is also recognized that the server modules mayhave to support multiple protocols and that some content provides 3, 7may provide no program interface protocols. A suitable language for useon the system is Network Query Language, commercially available from NQLInc., of South Coast Metro, Calif.

FIG. 6 is a flowchart of the method employed by the domain informationrobot 22. The domain method 200 begins a loop at step 205. There themethod first selects a DNS RegistryName from the DNS Table. At step 210,the Registry is queried for domain names created since the last suchquery, stored in the LastQueryTime field of the DNS Table. At step 215,a check for results is made. If no new domains were found, the loopcontinues by reverting to step 205.

If results were found at step 220, then processing continues to step225, which starts another loop. At step 225, the QueryTime field in theDNS Table is set to a valid timestamp for the query results, such as thevalue of a date/time field in the query result header. At step 230, adomain record is created in the Domain Table for the first new domainname. At step 235, the LastQueryTime field is updated with the time ofthe query, QueryTime. At step 240, the database updates are committed.At step 245, a call is made to the Whois Robot method, passing thedomain name, to obtain the related Whois data. At step 250, a check ismade to determine if there are other new records. If so, the methodreverts to step 225 to process the next domain name; otherwise, themethod reverts to step 205 to query another Registry.

FIG. 7 is a flowchart of the method employed by the registry retrievalrobot 32. The Whois method 300 has two entry points: a main entry pointat step 302 and a call interface entry point at step 307. The WHO method300 can be periodically executed to refresh registry data for previouslystored domains.

The main method begins at step 305, where the next DomainName field inthe Domain Table is read. At step 310, which is also the first step ofthe call interface entry 307, the method queries the associatedregistry, obtained from the RegistryPtr field, using an externalinterface to the registry database, such as a “WHOIS” service. Next, atstep 315, a local variable QueryTime is set to a valid timestamp for thequery, such as a value from a query result header.

At step 320, the method computes the checksum of the retrieved Whoisfile. At step 325, the resulting checksum is compared with the storedChecksum field of the Whois table WHOIS.Checksum. This is done so thatan unchanged Whois files is not stored, which would require a new Whoistable record. To save space and overhead, only changed files aretracked.

Consequently, a check is made at step 330. If the checksums match,processing reverts to step 305 to process the next Domain name. If thereis a difference in the checksums, processing continues to step 335.

At step 335, the file is stored as a compressed PDF file 39. At step340, a new Whois table record is created for the stored file 39. Thefields in the new record are updated with computed checksum and theQuery Time stamp. At step 345, the stored Whois 39 file is indexed bycalling the Indexer.

FIGS. 8A-8C are flowcharts of the method of the page retrieval robot 42.The PAGE method 400 begins in FIG. 8A. Beginning at step 402 (FIG. 8A),the method 400 selects the next second level domain from the DomainTable—Domain.Name. The domain server is then queried, at step 404, toreveal public files available from the current second level domain. Thedomain server returns a list of public files, the source files areretrieved and locally stored at step 406.

A loop through each public file begins at step 408. Once all the publicfiles have been processed for the current second level domain,processing returns to step 402 to select a new second level domain.Processing of individual public files begins at step 410.

At step 410, a local QueryTime field is set to a valid timestamp for thequery, such as the date/time field of the query result header, such asthe HTTP header. At step 412, a source checksum is computed from theretrieved source file for the public file. At step 414, the source isexecuted via browser software to yield a rendition of the source, whichis locally stored as a rendered file. For completeness, the source filecan be separately rendered in each browser explicitly supported by thesource code. At step 416, a checksum is computed from the rendered file.Turning to FIG. 8B at step 418, the method queries the Page Table for aURL record—PAGE.Url matching the public file name. If no match is found(step 420), processing jumps to step 430; otherwise processing jumps tostep 465 (FIG. 8C).

For a new page there will be no corresponding record in the Page Table.Although it is possible that a preexisting copy of the page has alreadybeen stored in the database under a different URL, for simplicity andeasy of description, it will be assumed that a renamed source file isstored separately. A removed page will result in a 404 error and theerror display can be stored under the URL.

For the new page a new Page Table record is created at step 430. The URLof the new page is stored in the Url field—PAGE.Url. The DomainPtr fieldis set to point to the Domain Table record of the second level domain.At step 432, the source file is converted to PDF format and stored inthe warehouse 12 as a source file 47. A new Source Table record iscreated at step 434 and pointed to by the PAGE. CurrentSourcePtr field.

In the new Source Table record, the UrlPtr is set to point to the newPage Table record. The Source Table fields can then be populated: theFilePtr points to the stored PDF source file, the Checksum field is setto the computed checksum, and the TimeStamp is set to the QueryTimevalue. The PrevSourcePtr and the NextSourcePtr are null. At step 436,the rendered file is converted to PDF format and stored in the warehouse12 as a rendered file 49. A new Render Table record is created at step438 and pointed to by the SOURCE.PageRenderPtr.

The new Render Table record can now be populated: the FilePtr points tothe stored PDF file, the Checksum field is set to the computed checksum,and the TimeStamp is set to the QueryTime value. The updates can now becommitted to the database at step 440. At step 442, the indexer isinvoked, passing the pointers to the files. Processing then reverts tostep 408.

To update preexisting URLs, the method follows the logic starting atstep 450 (FIG. 8C). At step 450, the source file checksum is comparedwith the checksum of the source file pointed to by the Page Tablerecord, namely PAGE.CurrentSourcePtr:FilePtr. If the source checksumsmatch (step 452), the source file has not been modified relative to thestored source file and the database is considered up to date andprocessing can revert to step 410; otherwise the database must beupdated.

To update the database, at step 454, the local source file is convertedto PDF format and stored in the warehouse 12 as a source file 47. A newrecord is created in the Source Table, at step 456, with the FilePtrfield pointing to the stored PDF source file, the source checksum storedin the Checksum field, and the QueryTime stored in the TimeStamp field.The PrevSourcePtr is set to point to the prior source record, which hasits NextSourcePtr set to point to the new record. The record is not yetrelated to a Render Table record. Processing then proceeds to step 438to process the rendered file.

If the source file is new, it cannot be assumed that its rendition isnew because much of the changeable text in the source file may not causea content change. In comparison, the rendition can change without achange in the source file because of counters, banners, or otherexternal content. To conserve storage space and to limit the amount ofredundant query results, such non-source related modifications are notstored in the database.

The rendered file is processed in much the same way as the source file.The rendered file checksum is compared, at step 458, with the checksumof the rendered file pointed to by the Page Table record, namelyPAGE.CurrentSourcePtr. If the rendered file checksums match, at step460, then the rendered file has not been modified relative to the storedrendered file; otherwise the new rendered file is stored. In eithercase, database relationships are updated.

To update the database in the case of an up-to-date rendered file, theSource Table record is updated at step 470. In particular, thePageRenderPtr field is set to point to the current record in the RenderTable. Note that there may be more than one Source Table record pointingto the same Render Table record. The many-to-one relationship helps toconserve storage requirements. At step 472, the database updates arecommitted to the database.

If the rendered file is new, the local rendered file is converted to PDFformat and stored in the warehouse 12 at step 480 as a rendered file 49.A new record is created in the Rendered Table, at step 482, with theFilePtr filed pointing to the stored PDF rendered file 49, the renderedfile checksum stored in the Checksum field, and the QueryTime stored inthe TimeStamp field. In the Source Table, the PageRenderPtr is set topoint to this Render Table record. The database relationships betweenthe Page, Source, and Render Tables are now set and the database updatescan now be committed to the database at step 484. The method theninvokes the indexer 15, at step 486, passing the respective FilePtrfields, to index the contents of the source and rendered files 47, 49.

Processing then loops back to step 410 to process the next file from thedomain server. Note that the illustrated method only processes publicfiles and does not mine database data from web sites. Such information,however, could be incorporated into the system by one of ordinary skillin the art.

FIG. 9 is a flowchart of the method of the user interface module 50. Afunction of the user interface module is to facilitate user access tothe archived information at a main interface 500. The method iscontrolled by a query type selection at step 508, which can include adomain name query 510, page query 520, text query 530, and a multimediaquery 540.

FIG. 10 illustrates an exemplary user interface for the query selectionmethod of FIG. 9. The interface 600 prompts the user to select one ofthe query types, each being hyperlinked 601, 602, 603, 604, 605 to arespective query interface.

Returning to FIG. 9, for a domain name query 510, the user provides asecond level domain name and possibly other parameters, such as a daterange, which are parsed at step 511. The method queries the domain table26 (FIG. 2) at step 512 and associated stored files to generate a domainregistration report at step 513. From the domain results, the page table44 (FIG. 2) can be queried at step 514 and a report can be generated atstep 515 to identify all the pages on a web site. With this query, thestate of the web site at a specific time can be reproduced with completeownership information, and historical source and image content.

FIG. 11 illustrates an exemplary user interface for the domain querymethod of FIG. 9. This interface presents the user with input fields. Adomain name 611 is a required input. A date range 612 and registrar 613fields can be used to narrow the query.

Returning to FIG. 9, for a page query 520, the user provides a specificURL and possibly other parameters, such as a date range, which areparsed at step 521. Here, in particular, the user can be associated witha remote Internet search engine 5 (FIG. 1) through a search engineinterface 505. The method 520 queries the Page Table 44 (FIG. 2) to findmatching records and associated stored files. From the query result, areport can be generated at step 523 to identify the history of thespecific URL. Using this query would allow a user to identify when aparticular content was incorporated into the page and how long it hadbeen there.

FIG. 12 illustrates an exemplary user interface for the page querymethod of FIG. 9. This interface 620 also presents the user with inputfields. A URL 621 is a required input, with an optional date range 622.

FIG. 13 illustrates an exemplary user interface for the search enginepage query method of FIG. 9. Shown is a possible search engine display690. As with prior art search engines, the display 690 provides a briefdescription of the identified web page 691 with a hyperlink to thecontent's URL 692. Also shown is a hyperlink 693 to the page querymethod 520. The link 693 automatically provides the specified URL as aparameter.

Returning to FIG. 9, for a text query 530, the user provides target text(either directly or indirectly via entry of a file location) andpossibly other parameters, such as a date range, which are parsed atstep 531. At step 532, the method queries the indexer 15 (FIG. 1),passing the target text, and the database tables 12 a (FIG. 1), based onthe parameters. The indexer returns a list of pointers to stored sourcefiles matching the target text. The results from the indexer query andthe database query are combined to generate a report to the user at step534. If the user is an interactive system user, the user can browse theresults and modify the query accordingly. To reduce the query effort,the intermediate query results from the indexer query and the databasequery are temporarily saved, for further use.

The results of the text query can also be filtered by a subcategory,such as registry (Whois) and source. That is, a searcher only interestedin Whois records can limit the query results to those records. Likewise,some searchers may only be interested in web page content and limittheir results to source and rendered files. Other users may restrict theresults to source files to identify metadata in the source files.

FIG. 14 illustrates an exemplary user interface for the text querymethod of FIG. 9. This interface 630 requests user entry of a querystring 631. The query string 631 can include boolean or other suitableoperators. The user can also enter a file location of a file having along text passage. The user can also provide a date range 632 to narrowthe query. In addition, the user can filter the query by specifyingstored files to exclude 634.

Returning to FIG. 9, the multimedia query 540 identifies multimedia(audio, video, image) files having content similar to a target contentprovided by the user. The method first parses query parameters at step541. At step 542, the method computes a signature for the targetcontent. The query is run at step 543 against the index and the tables.The target signature is passed to the indexer 15 (FIG. 2). The indexer15 can then return a list of pointers to multimedia files, ranked bysimilarity to the target content. The method also searches the SourceTable 46 (FIG. 2) and Render Table 48 (FIG. 2) based on suppliedparameters. The results from the indexer query and the database queryare combined to generate a multimedia report to the user at step 544. Ifthe user is an interactive system user, the user can browse the resultsand modify the query accordingly. To reduce the query effort, theintermediate query results from the indexer query and the database queryare temporarily saved, for further use.

FIG. 15 illustrates an exemplary user interface for the multimedia querymethod of FIG. 9. This interface 640 requests a filename 641, which canbe a local file or a remote file (including network files and Internetfiles). The query can be limited to a specific date range 642.

Returning to FIG. 9, it should be recognized that the system can supportadditional queries, such as ad hoc queries 550. At step 551, the queryis run, as entered by the user. A report is then generated, at step 552,for presentation to the user.

FIG. 16 illustrates an exemplary user interface for the ad hoc querymethod of FIG. 9. As shown, this interface 650 permits the user to enterany SQL query 651, which may be stored in a file, whose location isentered by the user.

Additional fields can also be added to the tables 12 a, such as a filetype field in the Source Table 46 or Whois fields in the Whois table 34,to improve query efficiency. Data from the tables 12 a can also bestored with the files 12 b as metadata indexed by the indexer. Thesystem can also include fuzzy logic to identify similar, but not exactmatches. The system can also incorporate a language translator tofacilitate locating foreign language equivalents. Additional queries canalso be added to the system to generate useful reports to the usercommunity.

Those of ordinary skill in the art should recognize that methodsinvolved in a data archival and retrieval system for internet workedcomputers may be embodied in a computer program product that includes acomputer-usable medium. For example, such a computer-usable medium caninclude a readable memory device, such as a solid state memory device, ahard drive device, a CD-ROM, a DVD-ROM, or a computer diskette, havingcomputer-readable program code segments stored thereon. Thecomputer-useable medium can also include a communications ortransmission medium, such as a bus or a communications link, eitheroptical, wired, or wireless, having program code segments carriedthereon as digital or analog data signals.

While the system has been particularly shown and described withreferences to particular embodiments, it will be understood by thoseskilled in the art that various changes in form and details may be made,without departing from the scope of the invention as claimed. Forexample, embodiments of the invention can be applied to variousenvironments, and are not limited to the described environment.Furthermore, embodiments of the invention are not limited to thearchival and retrieval of intellectual property references. As such,various embodiments of the invention can be encompassed by the appendedclaims.

I claim:
 1. A computerized system for retrieving content collected fromelectronic addresses over time, the content associated with aninternetworked content provider, comprising: a database storing data inan organized structure, the data including archived original content ascollected from an electronic address, the archived original contentassociated with a content provider; a plurality of modules populatingthe database with data associated with the archived original content; asearchable electronic index of the archived original content; a queryengine in communication with the electronic index for retrieving thestored data based on a query parameter and the electronic index; a userinterface in communication with the query engine for soliciting a queryfrom a user for desired content, the desired content having a matchwithin the archived original content; and a query result presented tothe user in response to the query and the electronic index, the queryresult including a representation of the archived original content andthe content provider.
 2. The system of claim 1 wherein the querysolicits desired content of at least one of a text string or amultimedia target.
 3. The system of claim 1 wherein the user interfaceincludes a search engine result identifying a Universal ResourceLocator.
 4. The system of claim 3 wherein the Universal Resource Locatoris responsive to the solicitation for a query.
 5. The system of claim 1wherein the query result includes a history of changes to the contentcollected from the electronic address over time.
 6. The system of claim1 wherein the query result includes a history of changes to the contentprovider over time.
 7. The system of claim 1 wherein the databaseassociates the archived original content with a content provider basedon a time that the archived original content was collected from theelectronic address.
 8. The system of claim 1 wherein the archivedoriginal content includes an image of browser-executable source code. 9.The system of claim 1 wherein the modules populate the database inresponse to actions of the content provider.
 10. The system of claim 9wherein the actions of the content provider include changes to content.11. A system for storing information for retrieval, comprising: adatabase storing data in an organized structure, the data associatedwith archived original content as collected from an electronic address,the content associated with a content provider; a plurality of modulespopulating the database with data associated with the data; a searchableelectronic index of the archived original content; and a query engine incommunication with the electronic index for retrieving the stored databased on a query parameter and the electronic index.
 12. The system ofclaim 11 wherein the database includes references to a plurality of datafiles for retrieval from the archive.
 13. The system of claim 11 whereinthe content provider includes a content provider selected from at leastone of a domain name service registry and a web server.
 14. The systemof claim 11 wherein the database relates the archived original contentwith a time that the archived original content was collected from theelectronic address.
 15. The system of claim 11 further comprising anindexer, the indexer creating the searchable electronic index.
 16. Thesystem of claim 11 wherein the searchable electronic index includesmultimedia data.
 17. The system of claim 11 wherein the archivedoriginal content includes an image of browser-executable source code.18. A computerized method for retrieving content collected fromelectronic addresses, the content associated with an internetworkedcontent provider, comprising: in a database, storing data in anorganized structure, the data including archived original content ascollected from an electronic address, the archived original contentassociated with a content provider; from a plurality of modules,populating the database with data associated with the archived originalcontent; preparing a searchable electronic index of the archivedoriginal content; coupling a query engine with the electronic index forretrieving the stored data based on a query parameter and the electronicindex; coupling a user interface with the query engine for soliciting aquery from a user for desired content, the desired content having amatch within the archived original content; and presenting a queryresult to the user in response to the query and the electronic index,the query result including a representation of the archived originalcontent and the content provider.
 19. The method of claim 18 wherein thequery solicits desired content of at least one of a text string or amultimedia target.
 20. The method of claim 18 wherein the user interfaceincludes a search engine result identifying a Universal ResourceLocator.
 21. The method of claim 20 wherein the Universal ResourceLocator is responsive to the solicitation for a query.
 22. The method ofclaim 18 wherein the query result includes a history of changes to thecontent collected from the electronic address over time.
 23. The methodof claim 18 wherein the query result includes a history of changes tothe content provider over time.
 24. The method of claim 18 whereinassociating the archived original content with a content provider isbased on a time that the archived original content was collected fromthe electronic address.
 25. The method of claim 18 wherein the archivedoriginal content includes an image of browser-executable source code.26. The method of claim 18 wherein populating the database is responsiveto actions of the content provider.
 27. The method of claim 26 whereinthe actions of the content provider include changes to content.
 28. Amethod for storing information for retrieval, comprising: in a database,storing data in an organized structure, the data associated witharchived original content as collected from an electronic address, thecontent associated with a content provider; from a plurality of modules,populating the database with data associated with the data; preparing asearchable electronic index of the archived original content; andcoupling a query engine with the electronic index for retrieving thestored data based on a query parameter and the electronic index.
 29. Themethod of claim 28 wherein the database includes references to aplurality of data files for retrieval from the archive.
 30. The methodof claim 28 wherein the content provider includes a content providerselected from at least one of a domain name service registry and a webserver.
 31. The method of claim 28 wherein the database relates thearchived original content with a time that the archived original contentwas collected from the electronic address.
 32. The method of claim 28further comprising coupling an indexer to the archived original content,the indexer creating the searchable electronic index.
 33. The method ofclaim 28 wherein the searchable electronic index includes multimediadata.
 34. The method of claim 28 wherein the archived original contentincludes an image of browser-executable source code.